Blockchain for communication of subscriber data records between public land mobile networks

ABSTRACT

Mechanisms for implementing a billing process between a first Public Land Mobile Network (PLMN1) and a second Public Land Mobile Network (PLMN2) for a subscriber of the PLMN1 that visits the PLMN2. A method comprises establishing a smart contract between the PLMN1, the PLMN2, and a Data Clearance House (DCH). The method comprises sending a subscriber usage record, represented by a distributed ledger, of the subscriber from the PLMN2 to the DCH using a blockchain upon the subscriber having visited the PLMN2, wherein the blockchain is based on the smart contract. The method comprises sending the subscriber usage record from the DCH to the PLMN1 using the blockchain.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a National stage of International Application No.PCT/IN2019/050193, filed Mar. 7, 2019, which is hereby incorporated byreference.

TECHNICAL FIELD

Embodiments presented herein relate to methods, a Data Clearance House(DCH) node, a node of a first Public Land Mobile Network (PLMN1), a nodeof a second Public Land Mobile Network (PLMN2), computer programs, and acomputer program product for implementing a billing process betweenPLMN1 and PLMN2 for a subscriber of PLMN1 that visits PLMN2.

BACKGROUND

In communications networks, there may be a challenge to obtain goodperformance and capacity for a given communications protocol, itsparameters and the physical environment in which the communicationsnetwork is deployed.

For example, roaming is the process where a subscriber is used outsidethe range of its home cellular network and connects to another availablecellular network. In such scenarios the resource usage as consumed bysubscriber when connecting to this other available cellular networkshould be recorded and handled correctly such that the subscriber can bebilled accordingly.

In some scenarios the transactions between the home network and theroaming network are handled through a data clearance house (DCH). Inmore detail, one primary aim of The DCH is to support wireless serviceproviders in managing their global roaming operations. In general theDCH might be responsible for handling the following services or subsetof services. The DCH might act as a roaming agreement broker by takingresponsibility for negotiation, preparation, and documentation ofroaming agreements on behalf of a PLMN. The DCH might handle roamingpartner management by acting as a single point of contact for managingmultiple roaming partners. The DCH might facilitate interstandardroaming. This includes, for example, management of different settlementand billing formats, signaling standards, switch incompatibilities, andproprietary extensions and of other technology issues. The DCH might beconfigured to handle data clearing and settlement by providing acentralized process for the exchange of call/data usage records of thesubscriber in terms of Transferred Account Procedures (TAP; includingits evolutions TAP2 and TAP3) data or Cellular Intercarrier BillingExchange Roamer (CIBER) data, monthly financial settlement, electronicdata delivery, management, and currency, etc. The DCH might beconfigured to handle conversion between different TAP formats. The DCHmight be configured to handle fraud management. For example, the DCHmight help network operators in early detection of frauds.

That is, the DCH is currently acting as a centric entity validating androuting the TAP file from the operator of the visiting PLMN of thesubscriber to the operator of the home PLMN of the subscriber. There iscurrently not any transparency in this file handling because thetransaction processing is offline and it can be tampered as thetransaction is mutable (i.e., liable to change). This could create aconflict between the operator of the visiting PLMN and the operator ofthe home PLMN, potentially causing a loss of revenue for the operator ofthe home PLMN. Current ways to handle this is to let the DCH generateinvoicing reports and evaluating the roaming transactions with theoperator of the home PLMN. However, this does not avoid the possibilitythat the call/data usage records are manipulated when being handled bythe DCH.

Hence, there is still a need for an improved handling of call/data usagerecords.

SUMMARY

An object of embodiments herein is to provide efficient handling ofcall/data usage records that does not suffer from the above issues, orat least where the above issues are mitigated or reduced.

According to a first aspect there is presented a method for implementinga billing process between a PLMN1 and a PLMN2 for a subscriber of thePLMN1 that visits the PLMN2. The method comprises establishing a smartcontract between the PLMN1, the PLMN2, and a DCH. The method comprisessending a subscriber usage record, represented by a distributed ledger,of the subscriber from the PLMN2 to the DCH using a blockchain upon thesubscriber having visited the PLMN2, wherein the blockchain is based onthe smart contract. The method comprises sending the subscriber usagerecord from the DCH to the PLMN1 using the blockchain.

According to a second aspect there is presented a system forimplementing a billing process between a PLMN1 and a PLMN2 for asubscriber of the PLMN1 that visits the PLMN2. The system comprises thePLMN1, the PLMN2, and a DCH. The system is configured to establish asmart contract between the PLMN1, the PLMN2, and the DCH. The system isconfigured to send a subscriber usage record, represented by adistributed ledger, of the subscriber from the PLMN2 to the DCH using ablockchain upon the subscriber having visited the PLMN2, wherein theblockchain is based on the smart contract. The system is configured tosend the subscriber usage record from the DCH to the PLMN1 using theblockchain.

According to a third aspect there is presented a method for implementinga billing process between a PLMN1 and a PLMN2 for a subscriber of thePLMN1 that visits the PLMN2. The method is performed by a DCH node. Themethod comprises establishing a smart contract between the PLMN1, thePLMN2, and the DCH. The method comprises obtaining a subscriber usagerecord, represented by a distributed ledger, of the subscriber from thePLMN2 and using a blockchain upon the subscriber having visited thePLMN2, wherein the blockchain is based on the smart contract. The methodcomprises sending the subscriber usage record to the PLMN1 using theblockchain.

According to a fourth aspect there is presented DCH node forimplementing a billing process between a PLMN1 and a PLMN2 for asubscriber of the PLMN1 that visits the PLMN2. The DCH node comprisesprocessing circuitry. The processing circuitry is configured to causethe DCH node to establish a smart contract between the PLMN1, the PLMN2,and the DCH. The processing circuitry is configured to cause the DCHnode to obtain a subscriber usage record, represented by a distributedledger, of the subscriber from the PLMN2 and using a blockchain upon thesubscriber having visited the PLMN2, wherein the blockchain is based onthe smart contract. The processing circuitry is configured to cause theDCH node to send the subscriber usage record to the PLMN1 using theblockchain.

According to a fifth aspect there is presented a computer program forimplementing a billing process between a PLMN1 and PLMN2 for asubscriber of PLMN1 that visits PLMN2, the computer program comprisingcomputer program code which, when run on processing circuitry of a DCHnode, causes the DCH node to perform a method according to the thirdaspect.

According to a sixth aspect there is presented a method for implementinga billing process between a PLMN1 and a PLMN2 for a subscriber of thePLMN1 that visits the PLMN2. The method is performed by a node in thePLMN2. The method comprises establishing a smart contract between thePLMN1, the PLMN2, and a DCH. The method comprises sending a subscriberusage record, represented by a distributed ledger, of the subscriber tothe PLMN1 via the DCH and using a blockchain upon the subscriber havingvisited the PLMN2, wherein the blockchain is based on the smartcontract.

According to a seventh aspect there is presented a node in a PLMN2 forimplementing a billing process between a PLMN1 and the PLMN2 for asubscriber of the PLMN1 that visits the PLMN2. The node comprisesprocessing circuitry. The processing circuitry is configured to causethe node to establish a smart contract between the PLMN1, the PLMN2, anda DCH. The processing circuitry is configured to cause the node to senda subscriber usage record, represented by a distributed ledger, of thesubscriber to the PLMN1 via the DCH and using a blockchain upon thesubscriber having visited the PLMN2, wherein the blockchain is based onthe smart contract.

According to an eight aspect there is presented a computer program forimplementing a billing process between a PLMN1 and PLMN2 for asubscriber of PLMN1 that visits PLMN2, the computer program comprisingcomputer program code which, when run on processing circuitry of a PLMN2node, causes the PLMN2 node to perform a method according to the sixthaspect.

According to a ninth aspect there is presented a method for implementinga billing process between a PLMN1 and a PLMN2 for a subscriber of thePLMN1 that visits the PLMN2. The method is performed by a node in thePLMN1. The method comprises establishing a smart contract between thePLMN1, the PLMN2, and a DCH. The method comprises obtaining a subscriberrecord, represented by a distributed ledger, of the subscriber from thePLMN2 via the DCH and using a blockchain upon the subscriber havingvisited the PLMN2, wherein the blockchain is based on the smartcontract.

According to a tenth aspect there is presented a node in a PLMN1 forimplementing a billing process between the PLMN1 and a PLMN2 for asubscriber of the PLMN1 that visits the PLMN2. The node comprisesprocessing circuitry. The processing circuitry is configured to causethe node to establish a smart contract between the PLMN1, the PLMN2, anda DCH. The processing circuitry is configured to cause the node toobtain a subscriber record, represented by a distributed ledger, of thesubscriber from the PLMN2 via the DCH and using a blockchain upon thesubscriber having visited the PLMN2, wherein the blockchain is based onthe smart contract.

According to an eleventh aspect there is presented a computer programfor implementing a billing process between a PLMN1 and PLMN2 for asubscriber of PLMN1 that visits PLMN2, the computer program comprisingcomputer program code which, when run on processing circuitry of a PLMN1node, causes the PLMN1 node to perform a method according to the ninthaspect.

According to a twelfth aspect there is presented a computer programproduct comprising a computer program according to at least one of thefourth aspect, the eighth aspect, and the eleventh aspect and a computerreadable storage medium on which the computer program is stored. Thecomputer readable storage medium can be a non-transitory computerreadable storage medium.

Advantageously these methods, these DCH nodes, these PLMN2 nodes, thesePLMN1 nodes, this system, and these computer programs provide efficienthandling of call/data usage records.

Advantageously, this avoids the above issues to be avoided.

Advantageously, this prevents any party from being able to update thetransactions without the approval from the PLMN1, the PLMN2, and theDCH.

Advantageously, any modification of the state of transactions will bevisible to the PLMN1, the PLMN2, and the DCH.

Other objectives, features and advantages of the enclosed embodimentswill be apparent from the following detailed disclosure, from theattached dependent claims as well as from the drawings.

Generally, all terms used in the claims are to be interpreted accordingto their ordinary meaning in the technical field, unless explicitlydefined otherwise herein. All references to “a/an/the element,apparatus, component, means, module, step, etc.” are to be interpretedopenly as referring to at least one instance of the element, apparatus,component, means, module, step, etc., unless explicitly statedotherwise. The steps of any method disclosed herein do not have to beperformed in the exact order disclosed, unless explicitly stated.

BRIEF DESCRIPTION OF THE DRAWINGS

The inventive concept is now described, by way of example, withreference to the accompanying drawings, in which:

FIG. 1 is a schematic diagram illustrating a communication systemaccording to embodiments;

FIGS. 2, 3, and 4 are flowcharts of methods according to embodiments;

FIG. 5 is a schematic diagram illustrating a blockchain according to anembodiment;

FIG. 6 is a signalling diagram of a method according to an embodiment;

FIG. 7 is a schematic diagram showing functional units of a DCH nodeaccording to an embodiment;

FIG. 8 is a schematic diagram showing functional modules of a DCH nodeaccording to an embodiment;

FIG. 9 is a schematic diagram showing functional units of a PLMN2 nodeaccording to an embodiment;

FIG. 10 is a schematic diagram showing functional modules of a PLMN2node according to an embodiment;

FIG. 11 is a schematic diagram showing functional units of a PLMN1 nodeaccording to an embodiment;

FIG. 12 is a schematic diagram showing functional modules of a PLMN1node according to an embodiment; and

FIG. 13 shows one example of a computer program product comprisingcomputer readable means according to an embodiment.

DETAILED DESCRIPTION

The inventive concept will now be described more fully hereinafter withreference to the accompanying drawings, in which certain embodiments ofthe inventive concept are shown. This inventive concept may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided by way of example so that this disclosure will be thorough andcomplete, and will fully convey the scope of the inventive concept tothose skilled in the art. Like numbers refer to like elements throughoutthe description. Any step or feature illustrated by dashed lines shouldbe regarded as optional.

FIG. 1 is a schematic diagram illustrating a communication system 100where embodiments presented herein can be applied. The communicationsystem 100 comprises a number of PLMN:s, here exemplified by a firstPLMN, denoted PLMN1, 110 and a second PLMN, denoted PLMN2 120, where thePLMN:s are configured to communicate through a DCH 150. As schematicallyillustrated in the figure, the DCH 150 comprises a DCH node 200.

As the skilled person understands, each of the PLMN:s comprises a numberof entities, functions, and devices, such as radio access network nodesin one or more radio access networks, and core network nodes in one ormore core networks. In particular, the PLMN1 110 comprises a PLMN1 node300 and the PLMN2 120 comprises a PLMN2 node 400, the functionalities ofwhich will be disclosed below. In some instances the PLMN1 node 300 willbe denoted a node in PLMN1, and the PLMN2 node 400 will be denoted anode in PLMN2.

The communication between the DCH node 200, the PLMN1 node 300, and thePLMN2 node 400 is facilitated by the use of a blockchain, and the PLMN1110, the PLMN2 120, and the DCH 150 in some aspects therefore areconsidered as being parts of a private blockchain network 130. Furtherdetails of how the DCH node 200, the PLMN1 node 300, and the PLMN2 node400 communicate by means of the blockchain will be disclosed below.

The private blockchain network 130 will act as a transparent partnerbilling settlement platform. However, entities outside the privateblockchain network 130 cannot modify, or even access, transactions ascommunicated between the PLMN1 110, the PLMN2 120, and the DCH 150 usingthe blockchain. Each of the DCH node 200, the PLMN1 node 300, and thePLMN2 node 400 stores a smart contract 240, 340, 440 for controlledaccess to the blockchain. Further, as schematically illustrated in thefigure, each of the DCH node 200, the PLMN1 node 300, and the PLMN2 node400 comprises a respective data storage 250, 350, 360 storing rateplans, subscriber details, etc.

The embodiments disclosed herein relate to mechanisms for implementing abilling process between PLMN1 110 and PLMN2 120 for a subscriber 140 ofPLMN1 110 that visits PLMN2 120. In this respect, the subscriber 140might be a terminal device, user equipment (UE), smartphone, networkequipped sensor, Internet of Things (IoT) device, network equippedvehicle, etc.

In order to obtain such mechanisms there is provided a DCH node 200, amethod performed by the DCH node 200, a computer program productcomprising code, for example in the form of a computer program, thatwhen run on processing circuitry of the DCH node 200, causes the DCHnode 200 to perform the method. In order to obtain such mechanisms thereis further provided a PLMN2 node 400, a method performed by the PLMN2node 400, and a computer program product comprising code, for example inthe form of a computer program, that when run on processing circuitry ofthe PLMN2 node 400, causes the PLMN2 node 400 to perform the method. Inorder to obtain such mechanisms there is further provided a PLMN1 node300, a method performed by the PLMN1 node 300, and a computer programproduct comprising code, for example in the form of a computer program,that when run on processing circuitry of the PLMN1 node 300, causes thePLMN1 node 300 to perform the method.

Reference is now made to FIG. 2 illustrating a method for implementing abilling process between a PLMN1 110 and PLMN2 120 for a subscriber 140of PLMN1 110 that visits PLMN2 120 as performed by the DCH node 200according to an embodiment.

S102: The DCH node 200 establishes a smart contract 240, 340, 440between the PLMN1 110, the PLMN2 120, and the DCH 150.

S104: The DCH node 200 obtains a subscriber usage record of thesubscriber 140 from the PLMN2 120. The subscriber usage record isobtained upon the subscriber 140 having visited the PLMN2 120. Thesubscriber usage record is represented by a distributed ledger. Thesubscriber usage record is obtained using a blockchain. The blockchainis based on the smart contract 240, 340, 440.S106: The DCH node 200 sends the subscriber usage record to the PLMN1110 using the blockchain.Embodiments relating to further details of this method will be disclosedbelow.Reference is now made to FIG. 3 illustrating a method for implementing abilling process between a PLMN1 110 and PLMN2 120 for a subscriber 140of PLMN1 110 that visits PLMN2 120 as performed by the PLMN2 node 400according to an embodiment.S202: The PLMN2 node 400 establishes a smart contract 240, 340, 440between the PLMN1 110, the PLMN2 120, and the DCH 150.S204: The PLMN2 node 400 sends a subscriber usage record of thesubscriber 140 to the PLMN1 110 via the DCH 150. The subscriber usagerecord is sent upon the subscriber 140 having visited the PLMN2 120. Thesubscriber usage record is represented by a distributed ledger. Thesubscriber usage record is sent using a blockchain. The blockchain isbased on the smart contract 240, 340, 440.Embodiments relating to further details of this method will be disclosedbelow.

Reference is now made to FIG. 4 illustrating a method for implementing abilling process between a PLMN1 110 and PLMN2 120 for a subscriber 140of PLMN1 110 that visits PLMN2 120 as performed by the PLMN1 node 300according to an embodiment.

S302: The PLMN1 node 300 establishes a smart contract 240, 340, 440between the PLMN1 110, the PLMN2 120, and the DCH 150.

S304: The PLMN1 node 300 obtains a subscriber 140 record of thesubscriber 140 from the PLMN2 120 via the DCH 150. The subscriber usagerecord is obtained upon the subscriber 140 having visited the PLMN2 120.The subscriber usage record is represented by a distributed ledger. Thesubscriber usage record is obtained using a blockchain. The blockchainis based on the smart contract 240, 340, 440.Embodiments relating to further details of all the above methodsdisclosed with reference to FIGS. 2, 3, and 4 will now be disclosed.

There could be different types of smart contracts 240, 340, 440. In someaspects the smart contracts 240, 340, 440 aggregate the services offeredby the PLMN2 120 (for subscribers 140 of PLMN1 110 that visits PLMN2120) and are shared by the PLMN1 110 with the DCH 150. In some aspectsthe smart contract 240, 340, 440 is related to rate plans as agreedbetween the PLMN1 110 and the PLMN2 120 and will hold the information ofagreed rate plans to process transaction data. That is, according to anembodiment, the smart contract 240, 340, 440 holds information of agreedrate plans between the PLMN1 110 and the PLMN2 120 for the PLMN2 120 toprocess transaction data, as represented by the subscriber usage record,for the subscriber 140. In some aspects the smart contract 240, 340, 440is related to rules for how the PLMN1 110, the PLMN2 120, and the DCH150 might access the subscriber usage record. That is, according to anembodiment, the smart contract 240, 340, 440 holds information of rulesfor controlling access to the subscriber usage record from the PLMN1110, the PLMN2 120, and the DCH 150. In some examples, according to thesmart contract 240, 340, 440, only the DCH 150 is allowed to, asrequired by the billing process, generate billing information from thesubscriber usage record.

By virtue of the blockchain, the subscriber usage record is maintainedin a safe and secured manner and enables transaction processing andcontrol of the usage of the subscriber usage record according toappropriate data access privileges. There may be different ways to formthe blockchain. FIG. 5 schematically illustrates a blockchain 500according to an embodiment. As is understood by the person skilled inthe art, a blockchain 500 is generally composed of N>1 blocks 510 a, 510b, . . . , 510N-1, 510N. The blocks 510 a:510N in the blockchain 500might hold batches of valid transactions 530 a, . . . , 530N-2, 530N-1that might be hashed and encoded into a Merkle tree. For eachtransaction a unique hash code will be generated. Each block 510 a:510Nmight include the cryptographic hash of the prior block 510 a:510N inthe blockchain 500, linking the blocks. Thereby, each transaction mightbe associated with the previous transaction hash code. The linked blocksform a chain. This iterative process confirms the integrity of theprevious block, all the way back to the original genesis block 510 a. Bymeans of the blockchain 500 all transactions are thereby made immutableand hence it is not possible to tamper with the transaction. Since thesmart contract 240, 340, 440 defines the trusted relation between theinvolved parties that make use of the blockchain 500, according to anembodiment, the smart contract 240, 340, 440 520 acts as, or is part ofa, genesis block of the blockchain 500.

A unique hash code could in the PLMN2 120, for example by the PLMN2 node400, be generated and included in the subscriber usage record for eachtransaction given rise to by the subscriber 140 having visited the PLMN2120. The hash code might be included in the blockchain 500 such thateach new transaction is associated with the hash code of any previoustransactions given rise to by the subscriber 140, or another subscriber140 of the PLMN1 110, having visited the PLMN2 120.

There could be different ways to send the subscriber usage record. Insome examples the subscriber usage record is sent as TAP in/TAP outfiles within the blockchain 500. As noted above, TAP is short forTransferred Account Procedures and could include its evolutions TAP2 andTAP3.

As noted above with reference to FIG. 1 , there might in addition to thePLMN1 110 and the PLMN2 120 be yet further PLMN:s. All other PLMN:s thanPLMN1 110 are herein therefore collectively denoted as PLMN2:s 120. Thatis in some examples there are more than one PLMN2 120. All, or some, ofthese PLMN2:s 120 might then be hierarchically related according tooperator precedence as defined by the PLMN1 110. For example, theremight be different privileges for the different PLMN2:s 120 asdetermined according to the operator precedence. Any number of PLMN:scan be involved in the transactions based on the operator precedencewith the appropriate privileges.

There might be different types of PLMN:s. In some examples the PLMN1 110is the home PLMN of the subscriber 140 and the PLMN2 120 is a visitorPLMN of the subscriber 140.

Additional aspects of the smart contract 240, 340, 440 will now bedisclosed.

As disclosed above, a private blockchain network 130 is used forhandling the subscriber usage records. In some aspects, the privateblockchain network 130 requires a hyperledger composer to be created. Ingeneral terms, as the skilled person understands, a hyperledger composeris a set of collaboration tools for building blockchain networks 130that enables the creation of smart contracts 240, 340, 440 andblockchain applications. Three primary configurations required to createa hyperledger composer are the creation of access control rules (aclfile), creation of CTO configuration to represent assets, participants,and transactions (.cto file), and configurations for maintaining thesmart contracts 240, 340, 440 (.js file). These primary configurationswill be described in the following.

As disclosed above, there are three partners associated with thetransactions; PLMN1 110, PLMN2 120, and DCH 150. As further disclosedabove, in some aspects only DCH 150 is enabled to modify thetransactions as the DCH 150 will perform the actual roaming transactionprocessing. However, in other aspects, for example based on the operatorprecedence and agreement, privileges in terms of modifying thetransactions might be set differently. Based on the operator precedence,different levels of transaction approval can be kept to each partner.

The PLMN1 110 and the PLMN2 will have a view privileges to thetransaction to verify the novelty of the transaction. A control file(.cto file) will be created for each partner. This control file willhold the assets and participant detail involved in the privateblockchain network 130. The smart contracts 240, 340, 440 are theentities which have the rating logic to perform the rating of a roamingtransaction and the aggregation logic to generate the partner settlementinvoices. The smart contracts 240, 340, 440 are maintained as a .js filein the hyperledger composer.

In summary, a method for implementing a billing process between PLMN1110 and PLMN2 120 for a subscriber 140 of the PLMN1 110 that visits thePLMN2 120 comprises:

S102, S202, S302: Establishing a smart contract 240, 340, 440 betweenthe PLMN1 110, the PLMN2 120, and the DCH 150.

S104, S204: Sending a subscriber usage record, represented by adistributed ledger, of the subscriber 140 from the PLMN2 120 to the DCH150 (and thus obtaining the subscriber usage record by the DCH 150 fromthe PLMN2 120) using a blockchain 500 upon the subscriber 140 havingvisited the PLMN2 120. The blockchain 500 is based on the smart contract240, 340, 440.S106, S304: Sending the subscriber usage record from the DCH 150 to thePLMN1 110 using the blockchain 500 (and thus obtaining the subscriberusage record by the PLMN1 110 from the DCH 150).

One particular embodiment for implementing a billing process betweenPLMN1 110 and PLMN2 120 for a subscriber 140 of the PLMN1 110 thatvisits the PLMN2 120 based on at least some of the above disclosedembodiments will now be disclosed in detail with reference to thesignalling diagram of FIG. 6 .

S401: The PLMN1 node 300, the PLMN2 node 400, and the DCH 150 establisha smart contract 240, 340, 440, as in above steps S102, S202, S302.

S402: The subscriber 140 of PLMN1 110 consumes data, or other resources,in the PLMN2 120.

S403: The PLMN2 node 400 sends, for example from a mobile switchingcenter, a subscriber usage record, for examples in the form of TAPin/TAP out files, of the subscriber 140 to the DCH 150, which thusobtains the subscriber usage record, as in above steps S104, S204.S404: The DCH 150 processes the subscriber usage record according to thesmart contract 240, 340, 440 to generate billing information for thesubscriber 140.S405: The DCH 150 sends the subscriber usage record, in the form ofbilling information, to the PLMN1 110 using the blockchain 500, whichthus obtains the subscriber usage record, as in steps S106, S304. Thesubscriber usage record might be received by a mobile switching centerin the PLMN1 110.FIG. 7 schematically illustrates, in terms of a number of functionalunits, the components of a DCH node 200 according to an embodiment.Processing circuitry 210 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1310 a (as in FIG. 13 ), e.g. in the form of a storage medium 230. Theprocessing circuitry 210 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 210 is configured to cause theDCH node 200 to perform a set of operations, or steps, as disclosedabove. For example, the storage medium 230 may store the set ofoperations, and the processing circuitry 210 may be configured toretrieve the set of operations from the storage medium 230 to cause theDCH node 200 to perform the set of operations. The set of operations maybe provided as a set of executable instructions. Thus the processingcircuitry 210 is thereby arranged to execute methods as hereindisclosed.

The storage medium 230 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The DCH node 200 may further comprise a communications interface 220 forcommunications with the PLMN1 node 300 and the PLMN2 node 400. As suchthe communications interface 220 may comprise one or more transmittersand receivers, comprising analogue and digital components.

The processing circuitry 210 controls the general operation of the DCHnode 200 e.g. by sending data and control signals to the communicationsinterface 220 and the storage medium 230, by receiving data and reportsfrom the communications interface 220, and by retrieving data andinstructions from the storage medium 230. Other components, as well asthe related functionality, of the DCH node 200 are omitted in order notto obscure the concepts presented herein.

FIG. 8 schematically illustrates, in terms of a number of functionalmodules, the components of a DCH node 200 according to an embodiment.The DCH node 200 of FIG. 8 comprises a number of functional modules; anestablish module 210 a configured to perform step S102, an obtain module210 b configured to perform step S104, and a send module 210 cconfigured to perform step S106. The DCH node 200 of FIG. 8 may furthercomprise a number of optional functional modules. In general terms, eachfunctional module 210 a-210 c may be implemented in hardware or insoftware. Preferably, one or more or all functional modules 210 a-210 cmay be implemented by the processing circuitry 210, possibly incooperation with the communications interface 220 and the storage medium230. The processing circuitry 210 may thus be arranged to from thestorage medium 230 fetch instructions as provided by a functional module210 a-210 c and to execute these instructions, thereby performing anysteps of the DCH node 200 as disclosed herein.FIG. 9 schematically illustrates, in terms of a number of functionalunits, the components of a PLMN2 node 400 according to an embodiment.Processing circuitry 310 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1310 b (as in FIG. 13 ), e.g. in the form of a storage medium 330. Theprocessing circuitry 310 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 310 is configured to cause thePLMN2 node 400 to perform a set of operations, or steps, as disclosedabove. For example, the storage medium 330 may store the set ofoperations, and the processing circuitry 310 may be configured toretrieve the set of operations from the storage medium 330 to cause thePLMN2 node 400 to perform the set of operations. The set of operationsmay be provided as a set of executable instructions. Thus the processingcircuitry 310 is thereby arranged to execute methods as hereindisclosed.

The storage medium 330 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The PLMN2 node 400 may further comprise a communications interface 320for communications with the PLMN1 node 300 and the DCH 150. As such thecommunications interface 320 may comprise one or more transmitters andreceivers, comprising analogue and digital components.

The processing circuitry 310 controls the general operation of the PLMN2node 400 e.g. by sending data and control signals to the communicationsinterface 320 and the storage medium 330, by receiving data and reportsfrom the communications interface 320, and by retrieving data andinstructions from the storage medium 330. Other components, as well asthe related functionality, of the PLMN2 node 400 are omitted in ordernot to obscure the concepts presented herein.

FIG. 10 schematically illustrates, in terms of a number of functionalmodules, the components of a PLMN2 node 400 according to an embodiment.The PLMN2 node 400 of FIG. 10 comprises a number of functional modules;an establish module 310 a configured to perform step S202, and a sendmodule 310 b configured to perform step S204. The PLMN2 node 400 of FIG.10 may further comprise a number of optional functional modules. Ingeneral terms, each functional module 310 a-310 b may be implemented inhardware or in software. Preferably, one or more or all functionalmodules 310 a-310 b may be implemented by the processing circuitry 310,possibly in cooperation with the communications interface 320 and thestorage medium 330. The processing circuitry 310 may thus be arranged tofrom the storage medium 330 fetch instructions as provided by afunctional module 310 a-310 b and to execute these instructions, therebyperforming any steps of the PLMN2 node 400 as disclosed herein.FIG. 11 schematically illustrates, in terms of a number of functionalunits, the components of a PLMN1 node 300 according to an embodiment.Processing circuitry 410 is provided using any combination of one ormore of a suitable central processing unit (CPU), multiprocessor,microcontroller, digital signal processor (DSP), etc., capable ofexecuting software instructions stored in a computer program product1310 c (as in FIG. 13 ), e.g. in the form of a storage medium 430. Theprocessing circuitry 410 may further be provided as at least oneapplication specific integrated circuit (ASIC), or field programmablegate array (FPGA).

Particularly, the processing circuitry 410 is configured to cause thePLMN1 node 300 to perform a set of operations, or steps, as disclosedabove. For example, the storage medium 430 may store the set ofoperations, and the processing circuitry 410 may be configured toretrieve the set of operations from the storage medium 430 to cause thePLMN1 node 300 to perform the set of operations. The set of operationsmay be provided as a set of executable instructions. Thus the processingcircuitry 410 is thereby arranged to execute methods as hereindisclosed.

The storage medium 330 may also comprise persistent storage, which, forexample, can be any single one or combination of magnetic memory,optical memory, solid state memory or even remotely mounted memory.

The PLMN1 node 300 may further comprise a communications interface 420for communications with the PLMN2 node 400 and the DCH 150. As such thecommunications interface 420 may comprise one or more transmitters andreceivers, comprising analogue and digital components.

The processing circuitry 410 controls the general operation of the PLMN1node 300 e.g. by sending data and control signals to the communicationsinterface 420 and the storage medium 430, by receiving data and reportsfrom the communications interface 420, and by retrieving data andinstructions from the storage medium 430. Other components, as well asthe related functionality, of the PLMN1 node 300 are omitted in ordernot to obscure the concepts presented herein.

FIG. 12 schematically illustrates, in terms of a number of functionalmodules, the components of a PLMN1 node 300 according to an embodiment.The PLMN1 node 300 of FIG. 12 comprises a number of functional modules;an establish module 410 a configured to perform step S302, and an obtainmodule 410 b configured to perform step S304. The PLMN1 node 300 of FIG.12 may further comprise a number of optional functional modules. Ingeneral terms, each functional module 410 a-410 b may be implemented inhardware or in software. Preferably, one or more or all functionalmodules 410 a-410 b may be implemented by the processing circuitry 410,possibly in cooperation with the communications interface 420 and thestorage medium 430. The processing circuitry 410 may thus be arranged tofrom the storage medium 430 fetch instructions as provided by afunctional module 410 a-410 b and to execute these instructions, therebyperforming any steps of the PLMN1 node 300 as disclosed herein.

Any of the DCH node 200, the PLMN1 node 300, and the PLMN2 node 400 maybe provided as a respective standalone device or as a part of at leastone further device. Thus, a first portion of the instructions performedby each of the DCH node 200, the PLMN1 node 300, and the PLMN2 node 400may be executed in a respective first device, and a second portion ofthe of the instructions performed by each of the DCH node 200, the PLMN1node 300, and the PLMN2 node 400 may be executed in a respective seconddevice; the herein disclosed embodiments are not limited to anyparticular number of devices on which the instructions performed by theDCH node 200, the PLMN1 node 300, and the PLMN2 node 400 may beexecuted. Hence, the methods according to the herein disclosedembodiments are suitable to be performed by a DCH node 200, a PLMN1 node300, and a PLMN2 node 400 residing in a cloud computational environment.Therefore, although a single processing circuitry 210, 310, 410 a isillustrated in FIGS. 7, 9, and 11 , the processing circuitry 210, 310,410 may be distributed among a plurality of devices, or nodes. The sameapplies to the functional modules 210 a-210 c, 310 a-310 b, 410 a-410 bof FIGS. 8, 10, and 12 and the computer programs 1310 a, 1310 b, 1310 cof FIG. 13 .

FIG. 13 shows one example of a computer program product 1310 a, 1310 b,1310 c comprising computer readable means 1330. On this computerreadable means 1330, a computer program 1320 a can be stored, whichcomputer program 1320 a can cause the processing circuitry 210 andthereto operatively coupled entities and devices, such as thecommunications interface 220 and the storage medium 230, to executemethods according to embodiments described herein. The computer program1320 a and/or computer program product 1310 a may thus provide means forperforming any steps of the DCH node 200 as herein disclosed. On thiscomputer readable means 1330, a computer program 1320 b can be stored,which computer program 1320 b can cause the processing circuitry 310 andthereto operatively coupled entities and devices, such as thecommunications interface 320 and the storage medium 330, to executemethods according to embodiments described herein. The computer program1320 b and/or computer program product 1310 b may thus provide means forperforming any steps of the PLMN2 node 400 as herein disclosed. On thiscomputer readable means 1330, a computer program 1320 c can be stored,which computer program 1320 c can cause the processing circuitry 410 andthereto operatively coupled entities and devices, such as thecommunications interface 420 and the storage medium 430, to executemethods according to embodiments described herein. The computer program1320 c and/or computer program product 1310 c may thus provide means forperforming any steps of the PLMN1 node 300 as herein disclosed.

In the example of FIG. 13 , the computer program product 1310 a, 1310 b,1310 c is illustrated as an optical disc, such as a CD (compact disc) ora DVD (digital versatile disc) or a Blu-Ray disc. The computer programproduct 1310 a, 1310 b, 1310 c could also be embodied as a memory, suchas a random access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM), or an electrically erasableprogrammable read-only memory (EEPROM) and more particularly as anon-volatile storage medium of a device in an external memory such as aUSB (Universal Serial Bus) memory or a Flash memory, such as a compactFlash memory. Thus, while the computer program 1320 a, 1320 b, 1320 c ishere schematically shown as a track on the depicted optical disk, thecomputer program 1320 a, 1320 b, 1320 c can be stored in any way whichis suitable for the computer program product 1310 a, 1310 b, 1310 c.

The inventive concept has mainly been described above with reference toa few embodiments. However, as is readily appreciated by a personskilled in the art, other embodiments than the ones disclosed above areequally possible within the scope of the inventive concept, as definedby the appended patent claims.

The invention claimed is:
 1. A method for implementing a billing processbetween a first Public Land Mobile Network (PLMN1) and a second PublicLand Mobile Network (PLMN2) for a subscriber of the PLMN1 that visitsthe PLMN2, the method comprising: establishing a smart contract amongthe PLMN1, the PLMN2, and a Data Clearance House (DCH); sending asubscriber usage record, represented by a distributed ledger, of thesubscriber from the PLMN2 to the DCH using a blockchain upon thesubscriber having visited the PLMN2, wherein the blockchain is based onthe smart contract; generating, at the DCH, billing information from thesubscriber usage record; and sending the billing information from theDCH to the PLMN1 using the blockchain.
 2. The method according to claim1, wherein the smart contract acts as, or is part of, a genesis block ofthe blockchain.
 3. The method according to claim 1, wherein a uniquehash code is in the PLMN2 generated and included in the subscriber usagerecord for each transaction given rise to by the subscriber havingvisited the PLMN2.
 4. The method according to claim 3, wherein the hashcode is included in the blockchain such that each new transaction isassociated with the hash code of any previous transactions given rise toby the subscriber, or another subscriber of the PLMN1, having visitedthe PLMN2.
 5. The method according to claim 1, wherein the subscriberusage record is sent as TAP (Transferred Account Procedures) in/TAP outfiles within the blockchain.
 6. The method according to claim 1, whereinthe smart contract holds information of agreed rate plans between thePLMN1 and the PLMN2 for the PLMN2 to process transaction data, asrepresented by the subscriber usage record, for the subscriber.
 7. Themethod according to claim 1, wherein the smart contract holdsinformation of rules for controlling access to the subscriber usagerecord from the PLMN1, the PLMN2, and the DCH.
 8. The method accordingto claim 1, wherein according to the smart contract, only the DCH isallowed to, as required by the billing process, generate the billinginformation from the subscriber usage record.
 9. The method according toclaim 1, wherein there are more than one PLMN2, and wherein the PLMN2sare hierarchically related according to operator precedence as definedby the PLMN1.
 10. The method according to claim 9, wherein there aredifferent privileges for different PLMN2s as determined according to theoperator precedence.
 11. The method according to claim 1, wherein thePLMN1 is a home PLMN of the subscriber and wherein the PLMN2 is avisitor PLMN of the subscriber.
 12. A method for implementing a billingprocess between a first Public Land Mobile Network (PLMN1), and a secondPublic Land Mobile Network (PLMN2), for a subscriber of the PLMN1 thatvisits the PLMN2, the method being performed by a Data Clearance House(DCH) node, the method comprising: establishing a smart contract amongthe PLMN1, the PLMN2, and the DCH; obtaining a subscriber usage record,represented by a distributed ledger, of the subscriber from the PLMN2and using a blockchain upon the subscriber having visited the PLMN2,wherein the blockchain is based on the smart contract; generatingbilling information from the subscriber usage record; and sending thebilling information to the PLMN1 using the blockchain.
 13. A method forimplementing a billing process between a first Public Land MobileNetwork (PLMN1), and a second Public Land Mobile Network (PLMN2), for asubscriber of the PLMN1 that visits the PLMN2, the method beingperformed by a node in the PLMN2, the method comprising: establishing asmart contract among the PLMN1, the PLMN2, and a Data Clearance House(DCH); and sending a subscriber usage record, represented by adistributed ledger, of the subscriber to the DCH using a blockchain uponthe subscriber having visited the PLMN2, wherein the blockchain is basedon the smart contract and wherein the DCH generates billing informationfrom the subscriber usage record, in which the DCH sends the billinginformation to the PLMN1 using the blockchain.
 14. A method forimplementing a billing process between a first Public Land MobileNetwork (PLMN1), and a second Public Land Mobile Network (PLMN2), for asubscriber of the PLMN1 that visits the PLMN2, the method beingperformed by a node in the PLMN1, the method comprising: establishing asmart contract among the PLMN1, the PLMN2, and a Data Clearance House(DCH); and obtaining, from the DCH, billing information generated from asubscriber record, in which the subscriber record originates from thePLMN2 upon the subscriber having visited the PLMN2 and the subscriberrecord represented by a distributed ledger of the subscriber and using ablockchain, wherein the blockchain is based on the smart contract andwherein the DCH sends the billing information using the blockchain.